Emergency signal for m2m devices

ABSTRACT

A method includes receiving, at a server connected to a network, a plurality of emergency alerts from a plurality of devices connected to the network. The method also includes analyzing, by the server, the plurality of emergency alerts to determine an emergency type of each of the plurality of emergency alerts. The method includes categorizing, by the server, the plurality of emergency alerts based on the emergency type of each of the plurality of emergency alerts. The method includes prioritizing a first category of the plurality of emergency alerts and consolidating the plurality of emergency alerts of the first category into a consolidated alert. The method includes causing the consolidated alert to be provided to an emergency responder.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to, and is a continuation of,co-pending U.S. patent application Ser. No. 14/841,816, filed on Sep. 1,2015, the contents of which are hereby incorporated by reference intheir entirety.

TECHNICAL FIELD

The technical field generally relates to managing messages frommachine-to-machine (M2M) devices and, more specifically, to systems andmethods for managing messages directed to a public-safety answeringpoint (PSAP).

BACKGROUND

As the number of M2M devices grows, more M2M devices may be detectingemergency conditions and communicating with a PSAP, without the need forhuman intervention. It is possible that multiple M2M devices in the sameroom, for example, may detect and transmit an emergency alert. It isfurther possible that multiple M2M devices may be transmitting alertsfor different emergencies of different priorities simultaneously. If aPSAP were to receive all of these messages, it may overload the PSAP. Asthe PSAP is how first responders become aware of emergencies, it isessential to public safety that the functionality of the PSAP bemaintained. Further, emergency alerts should be prioritized such thatthe PSAP processes high-priority alerts before processing low-priorityalerts. There is a need for methods and systems that decrease the loadon the PSAP by filtering and consolidating messages and that enable thePSAP to address more pressing matters first by prioritizing andthrottling messages.

SUMMARY

The disclosed systems and methods may allow for managing multiplemessages, or emergency alerts, by filtering, consolidating,prioritizing, or throttling messages to prevent overloading of a PSAP.

The present disclosure is directed to a method. The method may includereceiving, at a server connected to a network, a plurality of emergencyalerts from a plurality of devices connected to the network. The methodmay also include analyzing, by the server, the plurality of emergencyalerts to determine an emergency type of each of the plurality ofemergency alerts and categorizing, by the server, the plurality ofemergency alerts based on the emergency type of each of the plurality ofemergency alerts. The method may also include prioritizing a firstcategory of the plurality of emergency alerts and consolidating theplurality of emergency alerts of the first category into a consolidatedalert. The method may also include causing the consolidated alert to beprovided to an emergency responder.

The present disclosure is also directed to a method, which may includeproviding an emergency alert to an emergency responder, from a networkentity connected to a network, wherein the emergency alert is indicativeof an emergency and associated with a device connected to the network.The method may include receiving a location request from the emergencyresponder and identifying the device and identifying a network entitybased on the device. The method may also include providing the locationrequest and the device identity to the network entity, wherein thenetwork entity initiates a location services procedure to estimate alocation of the device. The method may include providing an emergencylocation to the emergency responder, the emergency location based on atleast the estimated location.

The present disclosure is also directed to a system. The system mayinclude a first device and a second device communicatively coupled to anetwork and a gateway communicatively coupled to a network and apublic-safety access point. The gateway may include instructions that,when executed by a processor of the gateway, cause the processor toeffectuate operations. The operations may include receiving a firstmessage from the first device, the first message indicative of a firstemergency condition detected by the first device and a second messagefrom the second device, the second message indicative of a secondemergency condition detected by the second device. The operations mayalso include determining, based on at least a relative location of thefirst device and the second device, whether the first emergencycondition and the second emergency condition are indicative of a sameemergency situation. The operations may also include, based on at leastthe first emergency condition and the second emergency condition beingindicative of the same emergency situation, consolidating the firstmessage and the second message into a consolidated alert to be providedto the public-safety access point.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the herein described telecommunications network are describedmore fully with reference to the accompanying drawings, which provideexamples. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide anunderstanding of the variations in implementing the disclosedtechnology. However, the instant disclosure may take many differentforms and should not be construed as limited to the examples set forthherein. Where practical, like numbers refer to like elements throughout.

FIG. 1 illustrates an exemplary telecommunication system in which a PSAPgateway may facilitate communications to a PSAP.

FIG. 2 is a schematic of an exemplary device that may transmit emergencyalerts intended for a PSAP.

FIG. 3 is a schematic of an exemplary network entity.

FIG. 4 is a flowchart of an exemplary process for providing emergencyalerts to a PSAP.

FIG. 5 is a flowchart of an exemplary process for providing emergencyalerts to a PSAP.

FIG. 6 is a diagram of an exemplary telecommunications system in whichthe disclosed methods and processes may be implemented.

FIG. 7 is an example system diagram of a radio access network and a corenetwork.

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a general packet radioservice (GPRS) network.

FIG. 9 illustrates an exemplary architecture of a GPRS network.

FIG. 10 illustrates an example block diagram view of a global system formobile communications (GSM)/GPRS/internet protocol (IP) multimedianetwork architecture.

FIG. 11 is a block diagram of an exemplary public land mobile network(PLMN).

DETAILED DESCRIPTION

FIG. 1 illustrates an exemplary telecommunication system 100 including aPSAP 102. In the context of the present disclosure, PSAP 102 maycomprise any appropriate type of equipment, such as, for example, acomputer, a server, a mobile device, a tablet, or any type of equipmentcapable of receiving and processing emergency alerts to dispatchemergency responders. It is to be understood that PSAP 102 as depictedherein is exemplary and not intended to be limiting. Acronyms are usedthroughout the disclosure that will be understood by those skilled inthe art.

Telecommunication system 100 may also include a PSAP gateway 104 incommunication with PSAP 102. PSAP gateway 104 may communicate through asubscriber network 106 (e.g., long term evolution (LTE), 5G, etc.). Forexample, PSAP gateway 104 may communicate with one or more M2M devices108, including M2M device 110, M2M device 112, or M2M device 114. PSAPgateway 104 may include any device capable of communicating throughsubscriber network 106. For example, PSAP gateway 104 may comprise anetwork entity. A network entity may comprise hardware or a combinationof hardware and software. PSAP gateway 104 may include or constitute acomponent or various components of a cellular broadcast system wirelessnetwork, a processor, a server, a gateway, a node, a mobile switchingcenter (MSC), a short message service center (SMSC), an ALFS, a gatewaymobile location center (GMLC), a radio access network (RAN), a servingmobile location center (SMLC), or the like, or any appropriatecombination thereof. PSAP gateway 104 may include, constitute, or becommunicatively coupled to a mobile management entity (MME). PSAPgateway 104 may constitute a single device or multiple devices (e.g.,single server or multiple servers, single gateway or multiple gateways,single controller or multiple controllers). PSAP gateway 104 maycommunicate wirelessly, via hard wire, or any appropriate combinationthereof.

M2M devices 108 may include any devices that are capable ofcommunicating with other devices in telecommunication system 100. M2Mdevices 108 may be configured to transmit emergency alerts based on atrigger, such as detecting an emergency condition. For example, M2Mdevice 110 may transmit an emergency alert upon detecting smoke.Similarly, M2M device 112 may be configured to transmit an emergencyalert upon detecting a temperature exceeding a threshold. As anotherexample, M2M device 114 may comprise a GPS that transmits an emergencyalert upon detecting that M2M device 114 has traveled a certain distanceor is located outside of a predefined geographical boundary. M2M devices108 may be configured to transmit emergency alerts over a control planeof subscriber network 106. Additionally or alternatively, M2M devices108 may be configured to transmit emergency alerts over a user plane ofsubscriber network 106.

Generally, emergency alerts may be received at PSAP 102. However, withthe large number of M2M devices 108, including M2M devices 108 that maytransmit duplicative or otherwise redundant emergency alerts, PSAP 102may become overloaded. To manage the load of PSAP 102, PSAP gateway 104may process emergency alerts received from M2M devices 108. It is to beunderstood that telecommunication systems 100 and 200 as depicted inFIGS. 1 and 2 are exemplary and not intended to be limiting.

FIG. 2 is a block diagram of an exemplary M2M device 108 that may beutilized with a telecommunication network as described herein. M2Mdevice 108 may comprise or be incorporated into any appropriate device,including nonconventional devices like a kitchen appliance, a motorvehicle control (e.g., steering wheel), or the like. For example, anyobject or thing embedded with hardware or software to enable the thingto exchange data may constitute M2M device 108. M2M devices 108 mayinclude devices across any industry. M2M devices 108 may be configuredto communicate directly or indirectly to PSAP gateway 104. M2M devices108 may include appliances or things not found in traditionaltelecommunication systems, including appliances, like dishwashers,vacuums, televisions, lighting or sound systems, or the like; sensorsdesigned to detect heart rate, smoke, temperature, sound, pressure,water, humidity, movement, or the like; vehicles, including airplanes,drones, automobiles, or the like; tracking devices affixed to livingthings or objects; or electronic devices, such as mobile devices,tablets, computers, or the like. M2M device 108 may be consideredstationary or portable. As evident from the herein description, UE, adevice, a communications device, or a mobile device is not to beconstrued as software per se.

Mobile device 102 may include any appropriate device, mechanism,software, or hardware for communicating with a telecommunication networkas described herein. In an example configuration, M2M device 108 maycomprise portions including a processor 200, a memory 202, or aninput/output 204. Each portion of M2M device 108 may comprise circuitryfor performing functions associated with each respective portion. Thus,each portion may comprise hardware or a combination of hardware andsoftware. Accordingly, each portion of M2M device 108 is not to beconstrued as software per se. It is emphasized that the block diagramdepiction of M2M device 108 is exemplary and not intended to imply aspecific implementation or configuration. For example, in an exampleconfiguration, M2M device 108 may comprise a cellular communicationstechnology, and processor 200 or memory 202 may be implemented, in partor in total, on a subscriber identity module (SIM) of M2M device 108. Inanother example configuration, M2M device 108 may comprise a laptopcomputer. The laptop computer may include a SIM, and various portions ofprocessor 200 or memory 202 may be implemented on the SIM, on the laptopother than the SIM, or any combination thereof.

Processor 200, memory 202, and input/output 204 may be coupled together(coupling not shown in FIG. 2) to allow communications therebetween.Input/output 204 may comprise a receiver of M2M device 108, atransmitter of M2M device 108, or a combination thereof. Input/output204 may be capable of receiving or providing information pertaining totelecommunications as described herein. In various configurations,input/output 204 may receive or provide information via any appropriatemeans, such as, for example, optical means (e.g., infrared),electromagnetic means (e.g., radio frequency (RF), Wi-Fi, Bluetooth®,ZigBee®), acoustic means (e.g., speaker, microphone, ultrasonicreceiver, ultrasonic transmitter), or a combination thereof. Forexample, as shown in FIG. 2, input/output 204 may include one or morewireless radios, such as Wi-Fi radio 206. For example, input/output 204may include one or more wireless radios dedicated to broadcast messages,for example, those receiving RF signals, such as a radio 208.

Processor 200 may be capable of performing functions pertaining totelecommunications, including, for example, communicating with otherdevices in or connected to subscriber network 106. In a basicconfiguration, M2M device 108 may include at least one memory 202, whichmay comprise executable instructions that, when executed by processor200, cause processor 200 to effectuate operations associated with atelecommunication network, such as subscriber network 106. Memory 202may comprise a storage medium having a concrete, tangible, physicalstructure. As is known, a signal does not have a concrete, tangible,physical structure. Memory 202, as well as any computer-readable storagemedium described herein, is not to be construed as a signal. Memory 202,as well as any computer-readable storage medium described herein, is notto be construed as a transient signal. Further, memory 202, as well asany computer-readable storage medium described herein, is not to beconstrued as a propagating signal. Memory 202, as well as anycomputer-readable storage medium described herein, is to be construed asan article of manufacture.

Memory 202 may store any information utilized in conjunction withtelecommunications. Depending upon the exact configuration or type ofprocessor, memory 202 may be volatile (such as some types of RAM),nonvolatile (such as ROM or flash memory), or a combination thereof. M2Mdevice 108 may include additional storage (e.g., removable storage ornonremovable storage) including, but not limited to, tape, flash memory,smart cards, CD-ROM, DVD, or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,universal serial bus (USB) compatible memory, or any other medium whichcan be used to store information and which can be accessed by M2M device108.

Mobile device 102 may be used to receive or transmit messages throughsubscriber network 106 from a sender, such as PSAP 102. It may beadvantageous for M2M device 108 or another device in or connected tosubscriber network 106 to communicate the location of M2M device 108 toPSAP gateway 104 or PSAP 102.

FIG. 3 is a block diagram of network entity 300 of a telecommunicationnetwork (e.g., subscriber network 104) as described herein. For example,PSAP gateway 104 may comprise, include, or communicate with networkentity 300. Network entity 300 may comprise hardware or a combination ofhardware and software. The functionality to facilitatetelecommunications via a telecommunications network may reside in anyone or combination of network entities 300. Network entity 300 depictedin FIG. 3 may represent or perform functionality of any appropriatenetwork entity 300, or combination of network entities 300, such as, forexample, a component or various components of a cellular broadcastsystem wireless network, a processor, a server, a gateway, a node, amobile switching center (MSC), a short message service center (SMSC), anALFS, a gateway mobile location center (GMLC), a radio access network(RAN), a serving mobile location center (SMLC), or the like, or anyappropriate combination thereof. It is emphasized that the block diagramdepicted in FIG. 3 is exemplary and not intended to imply a specificimplementation or configuration. Thus, network entity 300 may beimplemented in a single device or multiple devices (e.g., single serveror multiple servers, single gateway or multiple gateways, singlecontroller or multiple controllers). Multiple network entities may bedistributed or centrally located. Multiple network entities maycommunicate wirelessly, via hard wire, or any appropriate combinationthereof.

Network entity 300 may comprise a processor 302 and a memory 304 coupledto processor 302. Memory 304 may contain executable instructions that,when executed by processor 302, cause processor 302 to effectuateoperations associated with telecommunications via subscriber network106. As evident from the description herein, network entity 300 is notto be construed as software per se.

In addition to processor 302 and memory 304, network entity 300 mayinclude an input/output system 306. Processor 302, memory 304, andinput/output system 306 may be coupled together (coupling not shown inFIG. 3) to allow communications therebetween. Each portion of networkentity 300 may comprise circuitry for performing functions associatedwith each respective portion. Thus, each portion may comprise hardware,or a combination of hardware and software. Accordingly, each portion ofnetwork entity 300 is not to be construed as software per se.Input/output system 306 may be capable of receiving or providinginformation from or to a communications device or other network entitiesconfigured for telecommunications. For example input/output system 306may include a wireless communications (e.g., 2.5G/3G/4G/GPS) card.Input/output system 306 may be capable of receiving or sending videoinformation, audio information, control information, image information,data, or any combination thereof. Input/output system 306 may be capableof transferring information with network entity 300. In variousconfigurations, input/output system 306 may receive or provideinformation via any appropriate means, such as, for example, opticalmeans (e.g., infrared), electromagnetic means (e.g., RF, Bluetooth®,ZigBee®), acoustic means (e.g., speaker, microphone, ultrasonicreceiver, ultrasonic transmitter), or a combination thereof. In anexample configuration, input/output system 306 may comprise a Wi-Fifinder, a two-way GPS chipset or equivalent, or the like, or acombination thereof.

Input/output system 306 of network entity 300 also may containcommunication connection 308 that allows network entity 300 tocommunicate with other devices, network entities, or the like.Communication connection 308 may comprise communication media.Communication media typically embody computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. By way of example, and not limitation,communication media may include wired media such as a wired network ordirect-wired connection, or wireless media such as acoustic, RF,infrared, or other wireless media. The term computer-readable media asused herein includes both storage media and communication media.Input/output system 306 also may include an input device 310 such askeyboard, mouse, pen, voice input device, or touch input device.Input/output system 306 may also include an output device 312, such as adisplay, speakers, or a printer.

Processor 302 may be capable of performing functions associated withtelecommunications, such as functions for processing broadcast messages,as described herein. For example, processor 302 may be capable of, inconjunction with any other portion of network entity 300, determining atype of broadcast message and acting according to the broadcast messagetype or content, as described herein.

Memory 304 of network entity 300 may comprise a storage medium having aconcrete, tangible, physical structure. As is known, a signal does nothave a concrete, tangible, physical structure. Memory 304, as well asany computer-readable storage medium described herein, is not to beconstrued as a signal. Memory 304, as well as any computer-readablestorage medium described herein, is not to be construed as a transientsignal. Memory 304, as well as any computer-readable storage mediumdescribed herein, is not to be construed as a propagating signal. Memory304, as well as any computer-readable storage medium described herein,is to be construed as an article of manufacture.

Memory 304 may store any information utilized in conjunction withtelecommunications. Depending upon the exact configuration or type ofprocessor, memory 304 may include a volatile storage 314 (such as sometypes of RAM), a nonvolatile storage 316 (such as ROM, flash memory), ora combination thereof. Memory 304 may include additional storage (e.g.,a removable storage 318 or a nonremovable storage 320) including, forexample, tape, flash memory, smart cards, CD-ROM, DVD, or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, USB-compatible memory, or any othermedium that can be used to store information and that can be accessed bynetwork entity 300. Memory 304 may comprise executable instructionsthat, when executed by processor 302, cause processor 302 to effectuateoperations to provide broadcast messages to devices through subscribernetwork 106.

Returning to FIG. 1, an exemplary implementation of telecommunicationsystem 100 will be discussed. PSAP gateway 104 may be communicativelycoupled to PSAP 102 and network 106. PSAP gateway 104 may receive afirst message from M2M device 110. The first message may be indicativeof a first emergency condition detected by M2M device 110. For example,the first message may indicate an emergency (e.g., a fire) or acharacteristic of an emergency (e.g., smoke). PSAP gateway 104 mayreceive a second message from M2M device 112. The second message may beindicative of a second emergency condition detected by M2M device 112.For example, the second message may indicate an emergency (e.g., aflood) or a characteristic of an emergency (e.g., the presence ofwater). The emergency condition may indicate exceeding a temperaturethreshold, detection of smoke, detection of water, or detection of acollision. More examples of emergency conditions (e.g., emergencies andcharacteristics of emergencies) are discussed below with respect to FIG.4. PSAP gateway 104 may determine a relative location of M2M device 110and M2M device 112. For example, this may include determining a distancebetween M2M device 110 and M2M device 112, whether M2M device 110 andM2M device 112 are in the same vicinity (e.g., in the same building), orany other relative location between two devices. Based on the relativelocation, PSAP gateway 104 may determine whether the first emergencycondition and the second emergency condition are indicative of the sameemergency situation. For example, if M2M device 110 and M2M device 112are in the same room, they may be indicative of the same emergencysituation.

If the first emergency condition and the second emergency condition areindicative of the same emergency situation, gateway 104 may consolidatethe first message and the second message into a consolidated alert to beprovided to PSAP 102. For example, the consolidated message may indicatethe presence of both smoke and water at a location near M2M device 110or M2M device 112.

PSAP gateway 104 may determine a particular PSAP 102 to which to sendthe consolidated message. For example, PSAP gateway 104 may identify theparticular recipient based on the emergency type of the same emergencysituation identified by the first message and the second message. PSAPgateway 104 may identify PSAP 104 further based on a location of M2Mdevice 110 or M2M device 112. After identifying PSAP 104, PSAP gateway104 may provide the consolidated alert to PSAP 104.

If the first emergency condition and the second emergency condition arenot indicative of the same emergency, gateway PSAP 104 may determine thepriority of the first message based on the first condition and thepriority of the second message based on the second condition. Messagescan be prioritized based on any number of factors, including anemergency type indicated by the emergency condition. If the priority ofthe first message is higher than the priority of the second message(e.g., the first emergency condition indicates a life-threatening issueand the second emergency does not), PSAP gateway 104 may provide thefirst message to PSAP 102 prior to providing the second message to PSAP102.

If the first emergency condition and the second emergency condition arenot indicative of the same emergency, gateway PSAP 104 may determinewhether the second emergency condition is indicative of a non-emergencysituation. For example a message may indicate a condition that does notqualify as an emergency based on any number of factors. In someimplementations, emergencies to which first responders do not respond,such as a leaky faucet or a fence left open, may not be approvedemergency types. The approved emergency type may be based on a universallist of approved emergency types, or it may be based on a list ofapproved emergency types for a particular recipient. As another example,if the emergency type is a non-life-threatening theft, it may not be anapproved emergency type for a fire-station recipient. Whether anemergency type is an approved emergency type may be based on any numberof characteristics, including location of the source of the alert or therecipient, time (e.g., time of day or month), the recipient (e.g., firstresponder or guardian of infant), or any other factor. If the firstemergency condition and the second emergency condition are notindicative of the same emergency, and the second emergency condition isindicative of a non-emergency situation, PSAP gateway 104 may providethe first message to PSAP 102.

If the second emergency condition is not indicative of the sameemergency situation as the first emergency condition, PSAP gateway 104may determine an identity of a second PSAP 112 based on a location ofM2M device 112. Then, PSAP may provide the first message to PSAP 102 andthe second message to second PSAP 112.

FIG. 4 is a flowchart of an exemplary process 400 for providingemergency alerts to a PSAP. Process 400 may be implemented at least inpart by PSAP gateway 104, network entity 300, or a combination thereof.However, for simplicity, exemplary process 400 is described withreference to PSAP gateway 104. At step 402, PSAP gateway 104 may receivea plurality of emergency alerts from a plurality of devices, such as M2Mdevices 108. For example, PSAP gateway 104 may receive a first emergencyalert from M2M device 110, a second emergency alert from M2M device 112,or a third emergency alert from M2M device 114.

Emergency alerts may be indicative of a condition that may indicate anemergency or indicative of the emergency itself. For example, firstemergency alert may indicate an emergency condition. The emergencycondition may include a temperature threshold being exceeded, thepresence of water, the presence of smoke, or the presence of a substancethat exceeding a predefined threshold. The substance may be a chemicalor chemical compound, like carbon monoxide or arsenic. Additionally oralternatively, the substance may be a combination of chemicals, such asrat poison or other pesticides. The substance may be in any form,including solid, liquid, or gas. The predefined threshold may be zero,so that any detection of the substance would constitute an emergencycondition. For example, the emergency condition may include the presenceof carbon monoxide. As another example, the emergency condition mayinclude a level of carbon monoxide exceeding a predefined level. Forexample, very small amounts of carbon monoxide that may not be. Asanother example, second emergency alert may indicate a fire (anemergency). “Emergency” may be defined to encompass any number ofscenarios, events, occurrences, or situations, and need not be limitedto those types of emergencies addressed by emergency personnel or firstresponders. For example, an emergency may include, but not be limitedto, a fire, an earthquake, a flood, a tornado, a hurricane, any otherweather occurrence, a murder, a terrorist attack, an explosion, adetonation, a break-in, a trespassing, a kidnapping, a robbery, anyother removal of a living thing or object from a predefined location, anaccident, a collision, a car accident, a heart attack, a seizure, ashooting, any other health emergency, any other criminal-relatedemergency, an environmental or physical characteristic (e.g.,temperature or pressure) that has exceeded a threshold or is otherwiseoutside the bounds of an acceptable range, a poisoning, a contamination,or the like. Additionally, “emergency” may encompass even scenarios,events, occurrences, or situations that are not urgent. For example, anemergency may include, but not be limited to receiving a package or avisitor, a change in weather conditions, an animal water bowl beingempty, an infant awakening, a low battery level, a lack of power source,or the like. Generally, an emergency alert may be any message sent byany M2M device 108 designed to notify the recipient of a condition,scenario, event, occurrence, situation, or the like.

At step 404, PSAP gateway 104 may analyze the emergency alerts todetermine an emergency type of each alert. The alert itself may includean identifier of its type. Additionally or alternatively, PSAP gateway104 may determine the emergency type of an emergency alert based on thecontent or the source of the emergency alert. As an example, PSAPgateway 104 may determine that all emergency alerts from M2M device 110,which may be a smoke detector or a fire alarm, is a fire emergency type.Additionally or alternatively, PSAP gateway 104 may determine that anemergency alert indicating the presence of smoke is a fire emergencytype. As another example, PSAP gateway 104 may determine the emergencyalert type based on the location of M2M device 108. For example, PSAPgateway 104 may determine that emergency alerts from M2M devices 108located in a water tank of potable water indicate a contaminationemergency.

At step 406, PSAP gateway 104 may categorize the emergency alerts basedon the emergency type. For example, an emergency alert indicating smokefrom M2M device 110 and an emergency alert from fire alarm M2M device112 may be categorized as fire-related, life-threatening, high priority,or the like. An emergency alert indicating theft of a vehicle may becategorized as criminal activity, theft, or the like. Categorizing anemergency alert may be based on other sensed or determined information.For example, if it is determined that the vehicle contains passengers,the emergency alert indicating vehicle theft may be categorized as apossible-kidnapping, a possible car-jacking, life-threatening, or thelike. Alternatively, if it is determined that the stolen vehicle onlycontains the driver, the theft may be categorized asnon-life-threatening. Categorizing the emergency alert may also be basedon locations of M2M devices 108. For example, alerts from M2M devices110 and 112, which may be located in the same room of a building, may becategorized together.

At step 408, alerts in a first category may be consolidated. Forexample, alerts may be consolidated by combining the data contained inthe emergency alerts, deduping and merging the data, grouping the data,or the like. As an example, if multiple M2M devices 108 located in anapartment building provide emergency alerts, and each of the emergencyalerts indicates one or more of a fire, a temperature thresholdexceeded, or smoke, consolidating the emergency alerts may constitutecreating a consolidated alert that indicates a fire in the apartmentbuilding. As another example, the consolidated alert may indicate a firehas been detected in apartments A, B, and C of the apartment building.In this example, consolidating the message may include dedupingemergency alerts from multiple smoke detectors in apartment A ordeduping emergency alerts from a smoke detector and a thermometer inapartment A. According to some implementations, PSAP gateway 104 mayreceive multiple alerts from M2M device 110, and creating theconsolidated alert may include filtering the multiple alerts to removeduplicates (deduping), only including data from the most recent alert,or the like.

At step 410, PSAP gateway 104 may cause the consolidated alert to beprovided to the recipient. For example, step 410 may comprise PSAPgateway 104 providing the consolidated alert to a recipient. As anotherexample, PSAP gateway 104 may provide a message to the recipient thatthe consolidated alert is available for retrieval. Additionally oralternatively, the consolidated alert may be provided via a controlplane of network 106.

The recipient of the consolidated alert in step 410 may be any device orperson capable of receiving the consolidated alert. For example, if theconsolidated alert indicates that an infant has stopped breathing, therecipient may be a device associated with a parent, guardian, orcaretaker of the infant. Process 400 may comprise identifying therecipient. For example, the recipient may be identified based on theemergency type of the first category of messages. The consolidated alertmay be directed to an emergency responder, such as PSAP 102. Accordingto some implementations, process 400 may include determining a recipientbased on the consolidated alert or the emergency alert. This may includedetermining a recipient based on the emergency type. If the consolidatedalert is indicative of a fire, for example, the recipient may be PSAP102 that may be communicatively connected to a fire department.

Additionally or alternatively, the recipient may be identified based ona location associated with a respective one of the plurality of M2Mdevices 108 from which at least one of the plurality of emergency alertsof the first category was received. As an example, identifying therecipient may include identifying a plurality of recipients within ageographic area of the location. If the consolidated alert is indicativeof a fire, for example, the recipient may be PSAP 102 that may becommunicatively connected to a fire department that services thegeographical location of the fire or the recipient may be multiple PSAPs102 if, the location of the fire is between two or more fire departmentsthat are services by different PSAPs 102, or the like. As anotherexample, multiple recipients may be identified if the fire is so largethat requires responses from multiple fire departments.

Exemplary process 400 may include other steps. For example, additionalinformation from M2M devices 108 may be desirable. As an example, PSAPgateway 104 may identify additional information based on, for example,the type or content of data indicated by the emergency alerts and/or thetype of M2M devices 108. As another example, PSAP 102 may requestadditional information. PSAP gateway 104 may identify a subset of theM2M devices 108 from which the first category of emergency alerts wasreceived and request, from at least one of the devices of that subset,additional data regarding the emergency. For example, additional datamay include a location, the identity of other devices M2M device 108 candetect on the network, or other data indicative of a characteristic ofthe emergency, such as the temperature. In response, PSAP gateway 104may receive a supplemental message indicative of the additional data andprovide the additional data to the recipient. The additional data may beprovided via a control plane of network 106 or via a user plane ofnetwork 106.

FIG. 5 is a flowchart of an exemplary process 500 for providingemergency alerts to a PSAP. Process 500 may be implemented at least inpart by PSAP gateway 104, network entity 300, or a combination thereof.However, for simplicity, exemplary process 400 is described withreference to PSAP gateway 104. At step 502, PSAP gateway 104 may receivea plurality of emergency alerts from a plurality of devices, such as M2Mdevices 108. For example, PSAP gateway 104 may receive a first emergencyalert from M2M device 110, a second emergency alert from M2M device 112,or a third emergency alert from M2M device 114.

At step 504, PSAP gateway 104 may analyze the emergency alerts todetermine an emergency type of each alert. The alert itself may includean identifier of its type. Additionally or alternatively, PSAP gateway104 may determine the emergency type of an emergency alert based on thecontent or the source of the emergency alert. As an example, PSAPgateway 104 may determine that all emergency alerts from M2M device 110,which may be a smoke detector or a fire alarm, is a fire emergency type.Additionally or alternatively, PSAP gateway 104 may determine that anemergency alert indicating the presence of smoke is a fire emergencytype. As another example, PSAP gateway 104 may determine the emergencyalert type based on the location of M2M device 108. For example, PSAPgateway 104 may determine that emergency alerts from M2M devices 108located in a water tank of potable water indicate a contaminationemergency.

At step 506, PSAP gateway 104 may determine that a subset of theemergency alerts is for an approved emergency type. For example, not allemergency types may be approved. In some implementations, emergencies towhich first responders do not respond, such as a leaky faucet or a fenceleft open, may not be approved emergency types. The approved emergencytype may be based on a universal list of approved emergency types, or itmay be based on a list of approved emergency types for a particularrecipient. As another example, if the emergency type is anon-life-threatening theft, it may not be an approved emergency type fora fire-station recipient. Whether an emergency type is an approvedemergency type may be based on any number of characteristics, includinglocation of the source of the alert or the recipient, time (e.g., timeof day or month), the recipient (e.g., first responder or guardian ofinfant), or any other factor.

In some implementations, PSAP gateway 104 may provide an indication toM2M device 108 that sent an alert of an unapproved emergency typemessage that its alert was rejected. This may enable M2M device 108 totransmit its alert to a different device.

At step 508, PSAP gateway 104 may prioritize emergency alerts of anapproved emergency type. For example, if the emergency types of thealerts include a fire and a theft, the emergency alerts of the fire typemay be prioritized higher than the emergency alerts of the theft type.In some embodiments, it may be desirable to prioritize life-threateningemergency types over non-life-threatening emergency types.Prioritization may be based on a ranking of emergency types. Forexample, a second category of emergency messages may be prioritizedlower than the first category based on the emergency indicated by thefirst category (e.g., life-threatening) being ranked higher than theemergency indicated by the second category (e.g., non-life-threatening).Prioritization may be further based on any other factor, including thelocation of the emergency, the total number of recipients of the alerts,or the like.

At step 510, PSAP gateway 104 may provide the emergency alerts to therecipient in an order based on the prioritizing. For example, higherpriority emergencies may be provided prior to lower priorityemergencies. At least some of the emergency alerts may be provided tothe recipient via a control plane of network 106. In some embodiments,lower priority alerts may be provided to the recipient at a lowertransmission rate than is used for higher priority alerts. In someembodiments, lower priority alerts may be provided to the recipient at alower quality-of-service (“QoS”) level than is used for higher priorityalerts. In scenarios where there are multiple messages prioritized atthe same level (e.g., multiple messages having the same emergency type),process 500 may include consolidating multiple alerts into aconsolidated alert, and step 510 may include causing the consolidatedalert to be provided to the recipient.

As shown in FIG. 6, telecommunication system 600 may include wirelesstransmit/receive units (WTRUs) 602, a RAN 604, a core network 606, apublic switched telephone network (PSTN) 608, the Internet 610, or othernetworks 612, though it will be appreciated that the disclosed examplescontemplate any number of WTRUs, base stations, networks, or networkelements. Each WTRU 602 may be any type of device configured to operateor communicate in a wireless environment. For example, a WTRU maycomprise M2M device 108, a mobile device, network entity 300, or thelike, or any combination thereof. By way of example, WTRUs 602 may beconfigured to transmit or receive wireless signals and may include a UE,a mobile station, a mobile device, a fixed or mobile subscriber unit, apager, a cellular telephone, a PDA, a smartphone, a laptop, a netbook, apersonal computer, a wireless sensor, consumer electronics, or the like.WTRUs 602 may be configured to transmit or receive wireless signals overan air interface 614.

Telecommunication system 600 may also include one or more base stations616. Each of base stations 616 may be any type of device configured towirelessly interface with at least one of the WTRUs 602 to facilitateaccess to one or more communication networks, such as core network 606,PTSN 608, Internet 610, or other networks 612. By way of example, basestations 616 may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a site controller, an access point(AP), a wireless router, or the like. While base stations 616 are eachdepicted as a single element, it will be appreciated that base stations616 may include any number of interconnected base stations or networkelements.

RAN 604 may include one or more base stations 616, along with othernetwork elements (not shown), such as a base station controller (BSC), aradio network controller (RNC), or relay nodes. One or more basestations 616 may be configured to transmit or receive wireless signalswithin a particular geographic region, which may be referred to as acell (not shown). The cell may further be divided into cell sectors. Forexample, the cell associated with base station 616 may be divided intothree sectors such that base station 616 may include three transceivers:one for each sector of the cell. In another example, base station 616may employ multiple-input multiple-output (MIMO) technology and,therefore, may utilize multiple transceivers for each sector of thecell.

Base stations 616 may communicate with one or more of WTRUs 602 over airinterface 614, which may be any suitable wireless communication link(e.g., RF, microwave, infrared (IR), ultraviolet (UV), or visiblelight). Air interface 614 may be established using any suitable radioaccess technology (RAT).

More specifically, as noted above, telecommunication system 600 may be amultiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. Forexample, base station 616 in RAN 604 and WTRUs 602 connected to RAN 604may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish air interface 614 using wideband CDMA (WCDMA). WCDMA mayinclude communication protocols, such as High-Speed Packet Access (HSPA)or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink PacketAccess (HSDPA) or High-Speed Uplink Packet Access (HSUPA).

As another example base station 616 and WTRUs 602 that are connected toRAN 604 may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish air interface 614using LTE or LTE-Advanced (LTE-A).

Optionally base station 616 and WTRUs 602 connected to RAN 604 mayimplement radio technologies such as IEEE 602.16 (i.e., WorldwideInteroperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X,CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95(IS-95), Interim Standard 856 (IS-856), GSM, Enhanced Data rates for GSMEvolution (EDGE), GSM EDGE (GERAN), or the like.

Base station 616 may be a wireless router, Home Node B, Home eNode B, oraccess point, for example, and may utilize any suitable RAT forfacilitating wireless connectivity in a localized area, such as a placeof business, a home, a vehicle, a campus, or the like. For example, basestation 616 and associated WTRUs 602 may implement a radio technologysuch as IEEE 602.11 to establish a wireless local area network (WLAN).As another example, base station 616 and associated WTRUs 602 mayimplement a radio technology such as IEEE 602.15 to establish a wirelesspersonal area network (WPAN). In yet another example, base station 616and associated WTRUs 602 may utilize a cellular-based RAT (e.g., WCDMA,CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.As shown in FIG. 6, base station 616 may have a direct connection toInternet 610. Thus, base station 616 may not be required to accessInternet 610 via core network 606.

RAN 604 may be in communication with core network 606, which may be anytype of network configured to provide voice, data, applications, and/orvoice over internet protocol (VoIP) services to one or more WTRUs 602.For example, core network 606 may provide call control, billingservices, mobile location-based services, pre-paid calling, Internetconnectivity, video distribution or high-level security functions, suchas user authentication. Although not shown in FIG. 6, it will beappreciated that RAN 604 or core network 606 may be in direct orindirect communication with other RANs that employ the same RAT as RAN604 or a different RAT. For example, in addition to being connected toRAN 604, which may be utilizing an E-UTRA radio technology, core network606 may also be in communication with another RAN (not shown) employinga GSM radio technology.

Core network 606 may also serve as a gateway for WTRUs 602 to accessPSTN 608, Internet 610, or other networks 612. PSTN 608 may includecircuit-switched telephone networks that provide plain old telephoneservice (POTS). For LTE core networks, core network 606 may use IMS core614 to provide access to PSTN 608. Internet 610 may include a globalsystem of interconnected computer networks or devices that use commoncommunication protocols, such as the transmission control protocol(TCP), user datagram protocol (UDP), or IP in the TCP/IP internetprotocol suite. Other networks 612 may include wired or wirelesscommunications networks owned or operated by other service providers.For example, other networks 612 may include another core networkconnected to one or more RANs, which may employ the same RAT as RAN 604or a different RAT.

Some or all WTRUs 602 in telecommunication system 600 may includemulti-mode capabilities. That is, WTRUs 602 may include multipletransceivers for communicating with different wireless networks overdifferent wireless links. For example, one or more WTRUs 602 may beconfigured to communicate with base station 616, which may employ acellular-based radio technology, and with base station 616, which mayemploy an IEEE 802 radio technology.

FIG. 7 is an example system 700 including RAN 604 and core network 606.As noted above, RAN 604 may employ an E-UTRA radio technology tocommunicate with WTRUs 602 over air interface 614. RAN 604 may also bein communication with core network 606.

RAN 604 may include any number of eNode-Bs 702 while remainingconsistent with the disclosed technology. One or more eNode-Bs 702 mayinclude one or more transceivers for communicating with the WTRUs 602over air interface 614. Optionally, eNode-Bs 702 may implement MIMOtechnology. Thus, one of eNode-Bs 702, for example, may use multipleantennas to transmit wireless signals to, or receive wireless signalsfrom, one of WTRUs 602.

Each of eNode-Bs 702 may be associated with a particular cell (notshown) and may be configured to handle radio resource managementdecisions, handover decisions, scheduling of users in the uplink ordownlink, or the like. As shown in FIG. 7 eNode-Bs 702 may communicatewith one another over an X2 interface.

Core network 606 shown in FIG. 7 may include a mobility managementgateway or entity (MME) 704, a serving gateway 706, or a packet datanetwork (PDN) gateway 708. While each of the foregoing elements aredepicted as part of core network 606, it will be appreciated that anyone of these elements may be owned or operated by an entity other thanthe core network operator.

MME 704 may be connected to each of eNode-Bs 702 in RAN 604 via an S1interface and may serve as a control node. For example, MME 704 may beresponsible for authenticating users of WTRUs 602, bearer activation ordeactivation, selecting a particular serving gateway during an initialattach of WTRUs 602, or the like. MME 704 may also provide a controlplane function for switching between RAN 604 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

Serving gateway 706 may be connected to each of eNode-Bs 702 in RAN 604via the S1 interface. Serving gateway 706 may generally route or forwarduser data packets to or from the WTRUs 602. Serving gateway 706 may alsoperform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when downlink data isavailable for WTRUs 602, managing or storing contexts of WTRUs 602, orthe like.

Serving gateway 706 may also be connected to PDN gateway 708, which mayprovide WTRUs 602 with access to packet-switched networks, such asInternet 610, to facilitate communications between WTRUs 602 andIP-enabled devices.

Core network 606 may facilitate communications with other networks. Forexample, core network 606 may provide WTRUs 602 with access tocircuit-switched networks, such as PSTN 608, such as through IMS core614, to facilitate communications between WTRUs 602 and traditionalland-line communications devices. In addition, core network 606 mayprovide the WTRUs 602 with access to other networks 612, which mayinclude other wired or wireless networks that are owned or operated byother service providers.

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network as describedherein. In the example packet-based mobile cellular network environmentshown in FIG. 8, there are a plurality of base station subsystems (BSS)800 (only one is shown), each of which comprises a base stationcontroller (BSC) 802 serving a plurality of BTSs, such as BTSs 804, 806,808. BTSs 804, 806, 808 are the access points where users ofpacket-based mobile devices become connected to the wireless network. Inexample fashion, the packet traffic originating from mobile devices istransported via an over-the-air interface to BTS 808, and from BTS 808to BSC 802. Base station subsystems, such as BSS 800, are a part ofinternal frame relay network 810 that can include a service GPRS supportnodes (SGSN), such as SGSN 812 or SGSN 814. Each SGSN 812, 814 isconnected to an internal packet network 816 through which SGSN 812, 814can route data packets to or from a plurality of gateway GPRS supportnodes (GGSN) 818, 820, 822. As illustrated, SGSN 814 and GGSNs 818, 820,822 are part of internal packet network 816. GGSNs 818, 820, 822 mainlyprovide an interface to external IP networks such as PLMN 824, corporateintranets/internets 826, or Fixed-End System (FES) or the publicInternet 828. As illustrated, subscriber corporate network 826 may beconnected to GGSN 820 via a firewall 830. PLMN 824 may be connected toGGSN 820 via a boarder gateway router (BGR) 832. A Remote AuthenticationDial-In User Service (RADIUS) server 834 may be used for callerauthentication when a user calls corporate network 826.

Generally, there may be a several cell sizes in a GSM network, referredto as macro, micro, pico, femto or umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential or small businessenvironments. On the other hand, umbrella cells are used to covershadowed regions of smaller cells and fill in gaps in coverage betweenthose cells.

FIG. 9 illustrates an architecture of a typical GPRS network 900 asdescribed herein. The architecture depicted in FIG. 9 may be segmentedinto four groups: users 902, RAN 904, core network 906, and interconnectnetwork 908. Users 902 comprise a plurality of end users, who each mayuse one or more devices 910. Note that device 910 is referred to as amobile subscriber (MS) in the description of network shown in FIG. 9. Inan example, device 910 comprises a communications device (e.g., mobiledevice 102, mobile positioning center 116, network entity 300, any ofdetected devices 500, second device 508, access device 604, accessdevice 606, access device 608, access device 610 or the like, or anycombination thereof). Radio access network 904 comprises a plurality ofBSSs such as BSS 912, which includes a BTS 914 and a BSC 916. Corenetwork 906 may include a host of various network elements. Asillustrated in FIG. 9, core network 906 may comprise MSC 918, servicecontrol point (SCP) 920, gateway MSC (GMSC) 922, SGSN 924, home locationregister (HLR) 926, authentication center (AuC) 928, domain name system(DNS) server 930, and GGSN 932. Interconnect network 908 may alsocomprise a host of various networks or other network elements. Asillustrated in FIG. 9, interconnect network 908 comprises a PSTN 934, anFES/Internet 936, a firewall 1138, or a corporate network 940.

An MSC can be connected to a large number of BSCs. At MSC 918, forinstance, depending on the type of traffic, the traffic may be separatedin that voice may be sent to PSTN 934 through GMSC 922, or data may besent to SGSN 924, which then sends the data traffic to GGSN 932 forfurther forwarding.

When MSC 918 receives call traffic, for example, from BSC 916, it sendsa query to a database hosted by SCP 920, which processes the request andissues a response to MSC 918 so that it may continue call processing asappropriate.

HLR 926 is a centralized database for users to register to the GPRSnetwork. HLR 926 stores static information about the subscribers such asthe International Mobile Subscriber Identity (IMSI), subscribedservices, or a key for authenticating the subscriber. HLR 926 alsostores dynamic subscriber information such as the current location ofthe MS. Associated with HLR 926 is AuC 928, which is a database thatcontains the algorithms for authenticating subscribers and includes theassociated keys for encryption to safeguard the user input forauthentication.

In the following, depending on context, “mobile subscriber” or “MS”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 9, whenMS 910 initiates the attach process by turning on the networkcapabilities of the mobile device, an attach request is sent by MS 910to SGSN 924. The SGSN 924 queries another SGSN, to which MS 910 wasattached before, for the identity of MS 910. Upon receiving the identityof MS 910 from the other SGSN, SGSN 924 requests more information fromMS 910. This information is used to authenticate MS 910 together withthe information provided by HLR 926. Once verified, SGSN 924 sends alocation update to HLR 926 indicating the change of location to a newSGSN, in this case SGSN 924. HLR 926 notifies the old SGSN, to which MS910 was attached before, to cancel the location process for MS 910. HLR926 then notifies SGSN 924 that the location update has been performed.At this time, SGSN 924 sends an Attach Accept message to MS 910, whichin turn sends an Attach Complete message to SGSN 924.

Next, MS 910 establishes a user session with the destination network,corporate network 940, by going through a Packet Data Protocol (PDP)activation process. Briefly, in the process, MS 910 requests access tothe Access Point Name (APN), for example, UPS.com, and SGSN 924 receivesthe activation request from MS 910. SGSN 924 then initiates a DNS queryto learn which GGSN 932 has access to the UPS.com APN. The DNS query issent to a DNS server within core network 906, such as DNS server 930,which is provisioned to map to one or more GGSNs in core network 906.Based on the APN, the mapped GGSN 932 can access requested corporatenetwork 940. SGSN 924 then sends to GGSN 932 a Create PDP ContextRequest message that contains necessary information. GGSN 932 sends aCreate PDP Context Response message to SGSN 924, which then sends anActivate PDP Context Accept message to MS 910.

Once activated, data packets of the call made by MS 910 can then gothrough RAN 904, core network 906, and interconnect network 908, in aparticular FES/Internet 936 and firewall 1138, to reach corporatenetwork 940.

FIG. 10 illustrates an example block diagram view of a GSM/GPRS/IPmultimedia network architecture 1000 as described herein. Asillustrated, architecture 1000 includes a GSM core network 1002, a GPRSnetwork 1004 and an IP multimedia network 1006. GSM core network 1002includes an MS 1008, a BTS 1010, and a BSC 1012. MS 1008 is physicalequipment or mobile equipment, such as a mobile phone or a laptopcomputer that is used by mobile subscribers, with a SIM or a UniversalIntegrated Circuit Card (UICC). The SIM or UICC includes an IMSI whichis a unique identifier of a subscriber. BTS 1010 is physical equipment,such as a radio tower, that enables a radio interface to communicatewith MS 1008. Each BTS 1010 may serve more than one MS 1008. BSC 1012manages radio resources, including BTS 1010. BSC 1010 may be connectedto several BTSs 1010. BSC 1012 and BTS 1010 components, in combination,are generally referred to as a BSS or RAN 1014.

GSM core network 1002 also includes a MSC 1016, a GMSC 1018, an HLR1020, a visitor location register (VLR) 1022, an AuC 1024, and anequipment identity register (EIR) 1026. MSC 1016 performs a switchingfunction for the network. MSC 1016 also performs other functions, suchas registration, authentication, location updating, handovers, or callrouting. GMSC 1018 provides a gateway between GSM network 1002 and othernetworks, such as an Integrated Services Digital Network (ISDN) or PSTN1028. Thus, the GMSC 1018 provides interworking functionality withexternal networks.

HLR 1020 is a database that contains administrative informationregarding each subscriber registered in corresponding GSM network 1002.HLR 1020 also contains the current location of each MS. VLR 1022 is adatabase that contains selected administrative information from HLR1020. VLR 1022 contains information necessary for call control andprovision of subscribed services for each MS1008 currently located in ageographical area controlled by VLR 1022. HLR 1020 and VLR 1022,together with MSC 1016, provide the call routing and roamingcapabilities of GSM. AuC 1024 provides the parameters needed forauthentication and encryption functions. Such parameters allowverification of a subscriber's identity. EIR 1026 storessecurity-sensitive information about the mobile equipment.

An SMSC 1030 allows one-to-one short message service (SMS) messages tobe sent to or from MS 1008. A push proxy gateway (PPG) 1032 is used to“push” (i.e., send without a synchronous request) content to MS 1008.PPG 1032 acts as a proxy between wired and wireless networks tofacilitate pushing of data to MS 802. A short message peer-to-peer(SMPP) protocol router 1034 is provided to convert SMS-based SMPPmessages to cell broadcast messages. SMPP is a protocol for exchangingSMS messages between SMS peer entities such as short message servicecenters. The SMPP protocol is often used to allow third parties, e.g.,content suppliers such as news organizations, to submit bulk messages.

To gain access to GSM services, such as speech, data, or SMS, MS 1008first registers with the network to indicate its current location byperforming a location update and IMSI attach procedure. MS 1008 sends alocation update including its current location information to the MSC1016/VLR 1022, via BTS 1010 and the BSC 1012. The location informationis then sent to HLR 1020 of MS 1008. HLR 1020 is updated with thelocation information received from the MSC 1016/VLR 1022. The locationupdate also is performed when MS 1008 moves to a new location area.Typically, the location update is periodically performed to update thedatabase as location updating events occur.

GPRS network 1004 is logically implemented on GSM core network 1002architecture by introducing two packet-switching network nodes, an SGSN1036, a cell broadcast and a GGSN 1038. SGSN 1036 is at the samehierarchical level as MSC 1016 in GSM network 1002. SGSN 1036 controlsthe connection between GPRS network 1004 and MS 1008. SGSN 1036 alsokeeps track of individual MS 1008's locations and security functions andaccess controls.

A cell broadcast center (CBC) 1040 communicates cell broadcast messagesthat are typically delivered to multiple users in a specified area. Cellbroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile phone customers who arelocated within a given part of its network coverage area at the time themessage is broadcast.

GGSN 1038 provides a gateway between GPRS network 1002 and a PDN orother external IP networks 1042. That is, GGSN 1038 providesinterworking functionality with external networks, and sets up a logicallink to MS 1008 through SGSN 1036. When packet-switched data leaves GPRSnetwork 1004, it is transferred to a TCP-IP network 1042, such as anX.25 network or the Internet. In order to access GPRS services, MS 1008first attaches itself to GPRS network 1004 by performing an attachprocedure. MS 1008 then activates a PDP context, thus activating apacket communication session between MS 1008, SGSN 1036, and GGSN 1038.

In a GSM/GPRS network, GPRS services and GSM services can be used inparallel. MS 1008 can operate in one of three classes: class A, class B,and class C. A class A MS can attach to the network for both GPRSservices and GSM services simultaneously. A class A MS also supportssimultaneous operation of GPRS services and GSM services. For example,class A mobiles can receive GSM voice/data/SMS calls and GPRS data callsat the same time.

A class B MS can attach to the network for both GPRS services and GSMservices simultaneously. However, a class B MS does not supportsimultaneous operation of the GPRS services and GSM services. That is, aclass B MS can only use one of the two services at a given time.

A class C MS can attach for only one of the GPRS services and GSMservices at a time. Simultaneous attachment and operation of GPRSservices and GSM services is not possible with a class C MS.

GPRS network 1004 can be designed to operate in three network operationmodes (NOM1, NOM2 and NOM3). A network operation mode of GPRS network1004 is indicated by a parameter in system information messagestransmitted within a cell. The system information messages dictates MS1008 where to listen for paging messages and how to signal towards thenetwork. The network operation mode represents the capabilities of GPRSnetwork 1004. In a NOM1 network, MS 1008 can receive pages from acircuit switched domain (voice call) when engaged in a data call. MS1008 can suspend the data call or take both simultaneously, depending onthe ability of MS 1008 S. In a NOM2 network, MS 1008 may not receivepages from a circuit switched domain when engaged in a data call, sinceMS 1008 is receiving data and is not listening to a paging channel. In aNOM3 network, MS 1008 can monitor pages for a circuit switched networkwhile receiving data and vice versa.

IP multimedia network 1006 was introduced with 3GPP Release 5, andincludes an IP multimedia subsystem (IMS) 1044 to provide richmultimedia services to end users. A representative set of the networkentities within IMS 1044 are a call/session control function (CSCF), amedia gateway control function (MGCF) 1046, a media gateway (MGW) 1048,and a master subscriber database, called a home subscriber server (HSS)1050. HSS 1050 may be common to GSM network 1002, GPRS network 1004 aswell as IP multimedia network 1006.

IMS 1044 is built around the call/session control function, of whichthere are three types: an interrogating CSCF (I-CSCF) 1052, a proxy CSCF(P-CSCF) 1054, and a serving CSCF (S-CSCF) 1056. P-CSCF 1054 is the MS1008's first point of contact with IMS 1044. P-CSCF 1054 forwardssession initiation protocol (SIP) messages received from MS 1008 to anSIP server in a home network (and vice versa) of MS 1008. P-CSCF 1054may also modify an outgoing request according to a set of rules definedby the network operator (for example, address analysis or potentialmodification).

I-CSCF 1052 forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF 1056. I-CSCF 1052 may contact asubscriber location function (SLF) 1058 to determine which HSS 1050 touse for the particular subscriber, if multiple HSSs 1050 are present.S-CSCF 1056 performs the session control services for MS 1008. Thisincludes routing originating sessions to external networks and routingterminating sessions to visited networks. S-CSCF 1056 also decideswhether an application server (AS) 1060 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision is based on information received fromHSS 1050 (or other sources, such as AS 1060). AS 1060 also communicatesto a location server 1062 (e.g., a GMLC) that provides a position (e.g.,latitude/longitude coordinates) of MS 1008.

HSS 1050 contains a subscriber profile and keeps track of which corenetwork node is currently handling the subscriber. It also supportssubscriber authentication and authorization functions. In networks withmore than one HSS 1050, SLF 1058 may provide information on the HSS 1050that contains the profile of a given subscriber.

MGCF 1046 provides interworking functionality between SIP sessioncontrol signaling from IMS 1044 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown). It also controls a MGW 1048that provides user-plane interworking functionality (e.g., convertingbetween AMR- and PCM-coded voice). MGW 1048 also communicates with otherIP multimedia networks 1064.

PoC-capable mobile phones register with the wireless network when thephones are in a predefined area (e.g., job site, etc.). When the mobilephones leave the area, they register with the network in their newlocation as being outside the predefined area. This registration,however, does not indicate the actual physical location of the mobilephones outside the predefined area.

FIG. 11 illustrates a PLMN block diagram view of an example architecturethat may be replaced by a telecommunications system. In FIG. 11, solidlines may represent user traffic signals, and dashed lines may representsupport signaling. MS 1102 is the physical equipment used by the PLMNsubscriber. For example, M2M device 108, network entity 300, the like,or any combination thereof may serve as MS 1102. MS 1102 may be one of,but not limited to, a cellular telephone, a cellular telephone incombination with another electronic device or any other wireless mobilecommunication device.

MS 1102 may communicate wirelessly with BSS 1106. BSS 1106 contains BSC1108 and a BTS 1110. BSS 1106 may include a single BSC 1108/BTS 1110pair (base station) or a system of BSC/BTS pairs that are part of alarger network. BSS 1106 is responsible for communicating with MS 1102and may support one or more cells. BSS 1106 is responsible for handlingcellular traffic and signaling between MS 1102 and a core network 1118.Typically, BSS 1106 performs functions that include, but are not limitedto, digital conversion of speech channels, allocation of channels tomobile devices, paging, or transmission/reception of cellular signals.

Additionally, MS 1102 may communicate wirelessly with RNS 1112. RNS 1112contains a Radio Network Controller (RNC) 1114 and one or more Nodes B1116. RNS 1112 may support one or more cells. RNS 1112 may also includeone or more RNC 1114/Node B 1116 pairs or alternatively a single RNC1114 may manage multiple Nodes B 1116. RNS 1112 is responsible forcommunicating with MS 1102 in its geographically defined area. RNC 1114is responsible for controlling Nodes B 1116 that are connected to it andis a control element in a UMTS radio access network. RNC 1114 performsfunctions such as, but not limited to, load control, packet scheduling,handover control, security functions, or controlling MS 1102 access tocore network 1118.

An E-UTRA Network (E-UTRAN) 1120 is a RAN that provides wireless datacommunications for MS 1102 and user equipment 1104. E-UTRAN 1120provides higher data rates than traditional UMTS. It is part of the LIEupgrade for mobile networks, and later releases meet the requirements ofthe International Mobile Telecommunications (IMT) Advanced and arecommonly known as a 4G networks. E-UTRAN 1120 may include of series oflogical network components such as E-UTRAN Node B (eNB) 1122 and E-UTRANNode B (eNB) 1124. E-UTRAN 1120 may contain one or more eNBs. Userequipment 1104 may be any mobile device capable of connecting to E-UTRAN1120 including, but not limited to, a personal computer, laptop, mobiledevice, wireless router, or other device capable of wirelessconnectivity to E-UTRAN 1120. The improved performance of the E-UTRAN1120 relative to a typical UMTS network allows for increased bandwidth,spectral efficiency, and functionality including, but not limited to,voice, high-speed applications, large data transfer or IPTV, while stillallowing for full mobility.

An example of a mobile data and communication service that may beimplemented in the PLMN architecture described in FIG. 11 is EDGE. EDGEis an enhancement for GPRS networks that implements an improved signalmodulation scheme known as 8-PSK (phase shift keying). By increasingnetwork utilization, EDGE may achieve up to three times faster datarates as compared to a typical GPRS network. EDGE may be implemented onany GSM network capable of hosting a GPRS network, making it an idealupgrade over GPRS since it may provide increased functionality ofexisting network resources. Evolved EDGE networks are becomingstandardized in later releases of the radio telecommunication standards,which provide for even greater efficiency and peak data rates of up to 1Mbit/s, while still allowing implementation on existing GPRS-capablenetwork infrastructure.

Typically MS 1102 may communicate with any or all of BSS 1106, RNS 1112,or E-UTRAN 1120. In a illustrative system, each of BSS 1106, RNS 1112,and E-UTRAN 1120 may provide Mobile Station 1102 with access to corenetwork 1118. Core network 1118 may include of a series of devices thatroute data and communications between end users. Core network 1118 mayprovide network service functions to users in the circuit switched (CS)domain or the packet switched (PS) domain. The CS domain refers toconnections in which dedicated network resources are allocated at thetime of connection establishment and then released when the connectionis terminated. The PS domain refers to communications and data transfersthat make use of autonomous groupings of bits called packets. Eachpacket may be routed, manipulated, processed or handled independently ofall other packets in the PS domain and does not require dedicatednetwork resources.

The circuit-switched MGW function (CS-MGW) 1126 is part of core network1118, and interacts with VLR/MSC server 1128 and GMSC server 1130 inorder to facilitate core network 1118 resource control in the CS domain.Functions of CS-MGW 1126 include, but are not limited to, mediaconversion, bearer control, payload processing or other mobile networkprocessing such as handover or anchoring. CS-MGW 1118 may receiveconnections to MS 1102 through BSS 1106 or RNS 1112.

SGSN 1132 stores subscriber data regarding MS 1102 in order tofacilitate network functionality. SGSN 1132 may store subscriptioninformation such as, but not limited to, the IMSI, temporary identities,or PDP addresses. SGSN 1132 may also store location information such as,but not limited to, GGSN 1134 address for each GGSN where an active PDPexists. GGSN 1134 may implement a location register function to storesubscriber data it receives from SGSN 1132 such as subscription orlocation information.

Serving gateway (S-GW) 1136 is an interface which provides connectivitybetween E-UTRAN 1120 and core network 1118. Functions of S-GW 1136include, but are not limited to, packet routing, packet forwarding,transport level packet processing, or user plane mobility anchoring forinter-network mobility. PCRF 1138 uses information gathered from P-GW1136, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources or other networkadministration functions. PDN gateway (PDN-GW) 1140 may provideuser-to-services connectivity functionality including, but not limitedto, GPRS/EPC network anchoring, bearer session anchoring and control, orIP address allocation for PS domain connections.

HSS 1142 is a database for user information and stores subscription dataregarding MS 1102 or user equipment 1104 for handling calls or datasessions. Networks may contain one HSS 1142 or more if additionalresources are required. Example data stored by HSS 1142 include, but isnot limited to, user identification, numbering or addressinginformation, security information, or location information. HSS 1142 mayalso provide call or session establishment procedures in both the PS andCS domains.

VLR/MSC Server 1128 provides user location functionality. When MS 1102enters a new network location, it begins a registration procedure. A MSCserver for that location transfers the location information to the VLRfor the area. A VLR and MSC server may be located in the same computingenvironment, as is shown by VLR/MSC server 1128, or alternatively may belocated in separate computing environments. A VLR may contain, but isnot limited to, user information such as the IMSI, the Temporary MobileStation Identity (TMSI), the Local Mobile Station Identity (LMSI), thelast known location of the mobile station, or the SGSN where the mobilestation was previously registered. The MSC server may containinformation such as, but not limited to, procedures for MS 1102registration or procedures for handover of MS 1102 to a differentsection of core network 1118. GMSC server 1130 may serve as a connectionto alternate GMSC servers for other MSs in larger networks.

EIR 1144 is a logical element which may store the IMEI for MS 1102. Userequipment may be classified as either “white listed” or “black listed”depending on its status in the network. If MS 1102 is stolen and put touse by an unauthorized user, it may be registered as “black listed” inEIR 1144, preventing its use on the network. A MME 1146 is a controlnode which may track MS 1102 or user equipment 1104 if the devices areidle. Additional functionality may include the ability of MME 1146 tocontact idle MS 1102 or user equipment 1104 if retransmission of aprevious session is required.

As described herein, a telecommunications system wherein management andcontrol utilizing a software designed network (SDN) and a simple IP arebased, at least in part, on user equipment, may provide a wirelessmanagement and control framework that enables common wireless managementand control, such as mobility management, radio resource management,QoS, load balancing, etc., across many wireless technologies, e.g. LTE,Wi-Fi, and future 5G access technologies; decoupling the mobilitycontrol from data planes to let them evolve and scale independently;reducing network state maintained in the network based on user equipmenttypes to reduce network cost and allow massive scale; shortening cycletime and improving network upgradability; flexibility in creatingend-to-end services based on types of user equipment and applications,thus improve customer experience; or improving user equipment powerefficiency and battery life—especially for simple M2M devices—throughenhanced wireless management.

While examples of a telecommunications system in which emergency alertscan be processed and managed have been described in connection withvarious computing devices/processors, the underlying concepts may beapplied to any computing device, processor, or system capable offacilitating a telecommunications system. The various techniquesdescribed herein may be implemented in connection with hardware orsoftware or, where appropriate, with a combination of both. Thus, themethods and devices may take the form of program code (i.e.,instructions) embodied in concrete, tangible, storage media having aconcrete, tangible, physical structure. Examples of tangible storagemedia include floppy diskettes, CD-ROMs, DVDs, hard drives, or any othertangible machine-readable storage medium (computer-readable storagemedium). Thus, a computer-readable storage medium is not a signal. Acomputer-readable storage medium is not a transient signal. Further, acomputer-readable storage medium is not a propagating signal. Acomputer-readable storage medium as described herein is an article ofmanufacture. When the program code is loaded into and executed by amachine, such as a computer, the machine becomes an device fortelecommunications. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile or nonvolatile memory or storage elements), at least one inputdevice, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and may be combined withhardware implementations.

The methods and devices associated with a telecommunications system asdescribed herein also may be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,or via any other form of transmission, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, or thelike, the machine becomes an device for implementing telecommunicationsas described herein. When implemented on a general-purpose processor,the program code combines with the processor to provide a unique devicethat operates to invoke the functionality of a telecommunicationssystem.

While a telecommunications system has been described in connection withthe various examples of the various figures, it is to be understood thatother similar implementations may be used or modifications and additionsmay be made to the described examples of a telecommunications systemwithout deviating therefrom. For example, one skilled in the art willrecognize that a telecommunications system as described in the instantapplication may apply to any environment, whether wired or wireless, andmay be applied to any number of such devices connected via acommunications network and interacting across the network. Therefore, atelecommunications system as described herein should not be limited toany single example, but rather should be construed in breadth and scopein accordance with the appended claims.

What is claimed:
 1. A method comprising: receiving, at a serverconnected to a network, messages from a plurality of devices connectedto the network, wherein the messages comprise a first subset and secondsubset; consolidating the first subset into a consolidated message; andcausing the consolidated message to be provided to a recipient at afirst transport quality of service (QoS) level before causing anindication of the second subset to be provided to the recipient at alower QoS level than the first transport QoS level.
 2. The method ofclaim 1, wherein the second subset comprises at least one message of themessages.
 3. The method of claim 1, further comprising: categorizing atleast a portion of the messages into the first subset and the secondsubset, wherein each of the messages of the first subset share a messagetype.
 4. The method of claim 3, further comprising: identifying therecipient based on the message type or a location of at least one of theplurality of devices from which at least one of messages of the firstsubset was received.
 5. The method of claim 4, wherein identifying therecipient comprises identifying a plurality of recipients within ageographic region including the location.
 6. The method of claim 3,wherein the message type indicates an event to which the first subsetrelates.
 7. The method of claim 6, wherein the event comprises at leastone of an accident, a flood, a break-in, a terrorist threat, a robbery,a kidnapping, a poisoning, a health emergency, a murder, an explosion,or a tornado.
 8. The method of claim 1, wherein the plurality ofmessages are received on a control plane of the network.
 9. A methodcomprising: receiving messages at a server connected to a network;analyzing, by the server, the messages to determine a message type ofeach of the messages; categorizing a first subset of the messages basedon the message type of each of the messages of the first subset having afirst message type; prioritizing the first subset of the messages higherthan a second message of the messages based on the first message typeand a second message type of the second message; causing an indicationof the first subset to be provided to a recipient at a first transportquality of service (QoS) level; and causing an indication of the secondmessage to be provided to the recipient at a second transport QoS levelthat is less than the first transport QoS level.
 10. The method of claim9, further comprising: consolidating the first subset into aconsolidated message, wherein the indication of the first subsetcomprises the consolidated message.
 11. The method of claim 10, furthercomprising: determining that the message type of a third message of themessages is an unapproved message type; providing a response to thethird message indicating that the third message was rejected to a sourceof the third message.
 12. The method of claim 9, further comprising:identifying the recipient based on the first message type.
 13. Themethod of claim 9, further comprising: identifying the recipient basedon the second message type.
 14. A system comprising: an input/output forconnecting the system to a network; a processor communicatively coupledto the input/output; and memory storing instructions that cause theprocessor to effectuate operations, the operations comprising:receiving, via the network, a first message from a first device and asecond message from a second device, the first message indicative of afirst condition detected by the first device and the second messageindicative of a second condition detected by the second device;determining, based at least on a relative location of the first deviceto the second device whether the first condition and the secondcondition are indicative of a same situation; based on at least thefirst condition and the second condition being indicative of the samesituation, consolidating the first message and the second message into aconsolidated message; determining a first transport quality of service(QoS) level based at least on a priority of the same situation; andsending the consolidated message to a recipient at the first transportQoS level
 15. The system of claim 14, wherein the operations furthercomprise: receiving a third message; sending an indication of the thirdmessage to the recipient at a second transport QoS level that is lowerthan the first transport QoS level.
 16. The system of claim 14, whereinreceiving the first message and the second message comprises receiving atransmission on a control plane of the network.
 17. The system of claim14, wherein the first condition comprises at least one of exceeding atemperature threshold, presence of smoke, presence of water, exceeding asubstance threshold, or a collision.
 18. The system of claim 14, whereinthe same situation comprises at least one of an accident, a flood, abreak-in, a terrorist threat, a robbery, a kidnapping, a poisoning, ahealth emergency, a murder, an explosion, or a tornado.
 19. The systemof claim 14, wherein the operations further comprise: based at least ona type or a location of the same situation, identifying the recipient.20. The system of claim 19, wherein the recipient comprises apublic-safety answering point.